The following chart shows the recommended hardware specifications for a SSAS server.
| Component |
Umbria SSAS Server |
|---|---|
| Machine | Physical (virtual not recommended for production use) |
| Free Disk Space | 256 GB (SSD preferred) |
| RAM | See chart below |
| CPU Cores |
See chart below |
| OS Type/Family |
Windows |
| SQL Server | SQL Server 2016 Standard (SP1 recommended) or better |
Note:
SQL Server Standard has a 16GB memory limit for usage and processing of SSAS. Clients may need to move to SQL Server Enterprise if this limit affects them. Enterprise has the operating system maximum limit.
For more details, visit this Microsoft page: SQL Scale Limits
To determine the appropriate hardware requirements for your SSAS server, refer to the following table, which lists memory and CPU requirements based on the number of time entries or matters that you intend to import and maintain in Umbria. If the number of time entries and matters in your billing system correspond to two different requirement levels, use the higher of the two.
| Time Entries (Millions) | Matters (Thousands) | Memory | CPU Cores |
|---|---|---|---|
| < 5 | < 20 | 4 GB | 2 |
| 5–7.5 | 20–60 | 8 GB | 4 |
| 7.5–10 | 60–100 | 16 GB | 4 |
| 10–20 | 100–150 | 32 GB | 4 |
| 15–20 | 150–200 | 48 GB | 8 |
| 20–25 | 200–250 | 64 GB | 8 |
| 25+ | 250+ | 96 GB; per 10 mil time entries or 100k matters over number on left, add 16 GB RAM | 8; per 10 mil time entries or 100k matters over number on left, add 8 cores. |
In SQL Server 2016 SP1 Microsoft introduced support for NUMA architecture for SSAS so that multiple CPUs (in different sockets) would be supported. In the original SQL Server 2016 release there is no NUMA support for SSAS so having more than one CPU on the SSAS server is not beneficial.
Note: